Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d031d8c3baca10aae45e0013b62b8d8d870fa3d6cab8320e399f0de576c1e603

Tx prefix hash: 7b6859503e73659c0c53b6309a88a76ba12bb5eba844d79f6205c5d0cb6a97bc
Tx public key: a3571d1ad93467412898bbf456c66e2dfd1940d523177ed76dce295dbacdae38
Timestamp: 1737997488 Timestamp [UCT]: 2025-01-27 17:04:48 Age [y:d:h:m:s]: 00:140:22:01:35
Block: 1206371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100663 RingCT/type: yes/0
Extra: 01a3571d1ad93467412898bbf456c66e2dfd1940d523177ed76dce295dbacdae380211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b644d5eaf764ef5a35a4bc6d4b3ff3d66f2b237563bd9ce61e849c3101a6a2b2 0.600000000000 1693076 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": 1206381, "vin": [ { "gen": { "height": 1206371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b644d5eaf764ef5a35a4bc6d4b3ff3d66f2b237563bd9ce61e849c3101a6a2b2" } } ], "extra": [ 1, 163, 87, 29, 26, 217, 52, 103, 65, 40, 152, 187, 244, 86, 198, 110, 45, 253, 25, 64, 213, 35, 23, 126, 215, 109, 206, 41, 93, 186, 205, 174, 56, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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