Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 1d7d6ac95dbf85bef7aa614b07f37d48a86cfc982d16d0777b732bc0e7cbc246

Tx prefix hash: 879125774d30b635ee4f6a7edf3dd663ed15105635707b44f70cb1f13b2675fa
Tx public key: d56d5543b3e40152840b9b7d4a7f12ad3885ac3b34ce14f708bfd0407f381ef9
Timestamp: 1736128803 Timestamp [UCT]: 2025-01-06 02:00:03 Age [y:d:h:m:s]: 00:164:14:06:08
Block: 1191142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 117328 RingCT/type: yes/0
Extra: 01d56d5543b3e40152840b9b7d4a7f12ad3885ac3b34ce14f708bfd0407f381ef902110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27d1a448edc03a1bdbabd443846f9a4cc8228919d14aaf7bc0b30efc89e40e77 0.600000000000 1677665 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1191152, "vin": [ { "gen": { "height": 1191142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27d1a448edc03a1bdbabd443846f9a4cc8228919d14aaf7bc0b30efc89e40e77" } } ], "extra": [ 1, 213, 109, 85, 67, 179, 228, 1, 82, 132, 11, 155, 125, 74, 127, 18, 173, 56, 133, 172, 59, 52, 206, 20, 247, 8, 191, 208, 64, 127, 56, 30, 249, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8