Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd07b9b80bd287134fd6511148a05f4cf2026a67eecaaa0a8f80e8feed63e718

Tx prefix hash: 962300b91e888cda8dca659ed7875dfdb7393813164b57dee9c9a3ae3d26522a
Tx public key: d575fc8c40fac85b5d605f9f94b95ffb0781c7df33f4bd72b2c63d426b952451
Timestamp: 1744312621 Timestamp [UCT]: 2025-04-10 19:17:01 Age [y:d:h:m:s]: 00:225:05:09:40
Block: 1258617 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158690 RingCT/type: yes/0
Extra: 01d575fc8c40fac85b5d605f9f94b95ffb0781c7df33f4bd72b2c63d426b9524510211000000036c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 73319bfa7460bf2735b57dfb33cb9557802f7fb226a5d1ff74c5846462a992a8 0.600000000000 1745754 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": 1258627, "vin": [ { "gen": { "height": 1258617 } } ], "vout": [ { "amount": 600000000, "target": { "key": "73319bfa7460bf2735b57dfb33cb9557802f7fb226a5d1ff74c5846462a992a8" } } ], "extra": [ 1, 213, 117, 252, 140, 64, 250, 200, 91, 93, 96, 95, 159, 148, 185, 95, 251, 7, 129, 199, 223, 51, 244, 189, 114, 178, 198, 61, 66, 107, 149, 36, 81, 2, 17, 0, 0, 0, 3, 108, 152, 170, 61, 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