Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f2c8bc6166b8a56f16b09e97a1ec94a1c9351c03809314b1298b5d3652f0568

Tx prefix hash: 955b8d40f6663833ea7021d24789f71391f79cea9d28ea356a5b8e52d38f8c74
Tx public key: 73b4155a729f68a4ffb568d3513898af1ff0a32472774a321258fb2bf8cdc483
Timestamp: 1740918081 Timestamp [UCT]: 2025-03-02 12:21:21 Age [y:d:h:m:s]: 00:312:06:33:21
Block: 1230509 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221010 RingCT/type: yes/0
Extra: 0173b4155a729f68a4ffb568d3513898af1ff0a32472774a321258fb2bf8cdc4830211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59d43ef9c4227e01f9df53c3e9967b364cb328bb3fbf4f0d1fb92c419bfca0b6 0.600000000000 1717408 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": 1230519, "vin": [ { "gen": { "height": 1230509 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59d43ef9c4227e01f9df53c3e9967b364cb328bb3fbf4f0d1fb92c419bfca0b6" } } ], "extra": [ 1, 115, 180, 21, 90, 114, 159, 104, 164, 255, 181, 104, 211, 81, 56, 152, 175, 31, 240, 163, 36, 114, 119, 74, 50, 18, 88, 251, 43, 248, 205, 196, 131, 2, 17, 0, 0, 0, 3, 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