Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a573d9d49b4dcb7f48284d0f898ff127a9002a33551ca013ec6c5c0925f90c94

Tx prefix hash: bafd62a3939e1bb8f10978110dbd26f0ad1a8b0100ebf0b570d8d209a2c39e8a
Tx public key: 58e14172d09f94758a14b984e91688de91933e743c05a0963549df910019d9ef
Timestamp: 1750540824 Timestamp [UCT]: 2025-06-21 21:20:24 Age [y:d:h:m:s]: 00:224:22:49:33
Block: 1310014 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158547 RingCT/type: yes/0
Extra: 0158e14172d09f94758a14b984e91688de91933e743c05a0963549df910019d9ef02110000000325a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 720c6eaf8a0ec2a6c58759fb73e59e73eabf37294e8569befea23cbeb756797d 0.600000000000 1797631 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": 1310024, "vin": [ { "gen": { "height": 1310014 } } ], "vout": [ { "amount": 600000000, "target": { "key": "720c6eaf8a0ec2a6c58759fb73e59e73eabf37294e8569befea23cbeb756797d" } } ], "extra": [ 1, 88, 225, 65, 114, 208, 159, 148, 117, 138, 20, 185, 132, 233, 22, 136, 222, 145, 147, 62, 116, 60, 5, 160, 150, 53, 73, 223, 145, 0, 25, 217, 239, 2, 17, 0, 0, 0, 3, 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