Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f77550466e909b6ebcb27ccc4f3d06ee92a52b4f4a5a480d2cc96ced0b48d52

Tx prefix hash: 06bebc0fff48adfc43e8cde7c2462b8a52a9fa8332810589c816c2a70bdfbd15
Tx public key: 61e5fc3213302a675b1bbf4bf5c44d4e33fddfec284dc8fe14b553e8852ceaf8
Timestamp: 1748369272 Timestamp [UCT]: 2025-05-27 18:07:52 Age [y:d:h:m:s]: 00:177:07:31:45
Block: 1292209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124409 RingCT/type: yes/0
Extra: 0161e5fc3213302a675b1bbf4bf5c44d4e33fddfec284dc8fe14b553e8852ceaf802110000000286ae2f0d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cabc31a600302f756d365347c9738067025ab92adc33b63df1d6387ad8b2ec3 0.600000000000 1779680 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": 1292219, "vin": [ { "gen": { "height": 1292209 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cabc31a600302f756d365347c9738067025ab92adc33b63df1d6387ad8b2ec3" } } ], "extra": [ 1, 97, 229, 252, 50, 19, 48, 42, 103, 91, 27, 191, 75, 245, 196, 77, 78, 51, 253, 223, 236, 40, 77, 200, 254, 20, 181, 83, 232, 133, 44, 234, 248, 2, 17, 0, 0, 0, 2, 134, 174, 47, 13, 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