Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7aee50f180e0b818867bd2011fa6b110067de5ea5da151f05ab17a14d6a2bba8

Tx prefix hash: 38ae30b8f6c4acd237e00e6fc1aa37547cf61dc6c423854afe1d881782a5ba5d
Tx public key: bd3b1d573e7498e07de91d5062221c6b7b82f4774c0905c55d918cd22296944e
Timestamp: 1736600538 Timestamp [UCT]: 2025-01-11 13:02:18 Age [y:d:h:m:s]: 00:158:02:46:05
Block: 1195037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112718 RingCT/type: yes/0
Extra: 01bd3b1d573e7498e07de91d5062221c6b7b82f4774c0905c55d918cd22296944e0211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1614a510eaeaac7a9be87f45d1d675e65448ef289c2a9250a71add72a0c53356 0.600000000000 1681622 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": 1195047, "vin": [ { "gen": { "height": 1195037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1614a510eaeaac7a9be87f45d1d675e65448ef289c2a9250a71add72a0c53356" } } ], "extra": [ 1, 189, 59, 29, 87, 62, 116, 152, 224, 125, 233, 29, 80, 98, 34, 28, 107, 123, 130, 244, 119, 76, 9, 5, 197, 93, 145, 140, 210, 34, 150, 148, 78, 2, 17, 0, 0, 0, 6, 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