Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 647a38e2df0b2351e7fc186be74d1aba95dadd429c37474c31b46c1aa85a7898

Tx prefix hash: af862383ac8b1cd719c586c74f296b4a5ef63d867ddda4edfa4b956a62118ae4
Tx public key: ef85c29bcf8e1da390dce9460e8e752e393a94c1ae15c9c1916d609c87ac40c7
Timestamp: 1737571732 Timestamp [UCT]: 2025-01-22 18:48:52 Age [y:d:h:m:s]: 00:150:02:49:26
Block: 1203036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106990 RingCT/type: yes/0
Extra: 01ef85c29bcf8e1da390dce9460e8e752e393a94c1ae15c9c1916d609c87ac40c70211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4986975a242c9846b67a16704ceecc0889ad413b01b5f792b786dcee3dff4ed2 0.600000000000 1689709 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": 1203046, "vin": [ { "gen": { "height": 1203036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4986975a242c9846b67a16704ceecc0889ad413b01b5f792b786dcee3dff4ed2" } } ], "extra": [ 1, 239, 133, 194, 155, 207, 142, 29, 163, 144, 220, 233, 70, 14, 142, 117, 46, 57, 58, 148, 193, 174, 21, 201, 193, 145, 109, 96, 156, 135, 172, 64, 199, 2, 17, 0, 0, 0, 4, 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