Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cbd541d38eceda37958b7df9d8135a71566f047a9098e34cf5d446851b24c48a

Tx prefix hash: 99d9ff82acce0a1e9a8b80ce3a52ff9c2bb3df7bbffb27fed515aa442c86baa4
Tx public key: fbdfd85f85374eef9cf746302ef669c8baf87d15d32833c3a2d20c09c569c6e0
Timestamp: 1747752984 Timestamp [UCT]: 2025-05-20 14:56:24 Age [y:d:h:m:s]: 00:185:02:45:31
Block: 1287107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129993 RingCT/type: yes/0
Extra: 01fbdfd85f85374eef9cf746302ef669c8baf87d15d32833c3a2d20c09c569c6e00211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b82c71ed4183b95a046c89c766e8107a88f1d17d997038c66ee5449727b382ed 0.600000000000 1774574 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": 1287117, "vin": [ { "gen": { "height": 1287107 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b82c71ed4183b95a046c89c766e8107a88f1d17d997038c66ee5449727b382ed" } } ], "extra": [ 1, 251, 223, 216, 95, 133, 55, 78, 239, 156, 247, 70, 48, 46, 246, 105, 200, 186, 248, 125, 21, 211, 40, 51, 195, 162, 210, 12, 9, 197, 105, 198, 224, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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