Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 311725f7a0b268acd6f987e74c2b6a6d93d9b85f39816f17b42c61ab708f2c76

Tx prefix hash: e57a125b2350480638c7d3189ae8fa5d9c2465b4400b687be9eecca48e1acbcc
Tx public key: df1fe14f0af825446efe56562f6c3f0e956c526a55856d55253323dc43b61d87
Timestamp: 1704047811 Timestamp [UCT]: 2023-12-31 18:36:51 Age [y:d:h:m:s]: 01:117:22:03:36
Block: 925293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 345414 RingCT/type: yes/0
Extra: 01df1fe14f0af825446efe56562f6c3f0e956c526a55856d55253323dc43b61d8702110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9225ce1292a5530789f4efa9bceff7f1f200aacd3e936a386e178ba92c8897f 0.600000000000 1383053 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": 925303, "vin": [ { "gen": { "height": 925293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9225ce1292a5530789f4efa9bceff7f1f200aacd3e936a386e178ba92c8897f" } } ], "extra": [ 1, 223, 31, 225, 79, 10, 248, 37, 68, 110, 254, 86, 86, 47, 108, 63, 14, 149, 108, 82, 106, 85, 133, 109, 85, 37, 51, 35, 220, 67, 182, 29, 135, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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