Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e7ed818c83210bb88ed7994174a8a803e9023977feb9e465119abb2af4ae202

Tx prefix hash: 4515dffc50b9d1add3c247294894754e442f12521d7a5bae6253c14b6053d92a
Tx public key: 34d9f82fcfe8fd7be30dd8f29aa9a1a7fc69d147e46b4631bb4a03af92dda688
Timestamp: 1704932640 Timestamp [UCT]: 2024-01-11 00:24:00 Age [y:d:h:m:s]: 01:089:22:10:33
Block: 932627 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325370 RingCT/type: yes/0
Extra: 0134d9f82fcfe8fd7be30dd8f29aa9a1a7fc69d147e46b4631bb4a03af92dda6880211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b336e8d501eabecb3fe9fa5d7af37dca4bf284d9da936697d888093c4f33fef0 0.600000000000 1390565 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": 932637, "vin": [ { "gen": { "height": 932627 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b336e8d501eabecb3fe9fa5d7af37dca4bf284d9da936697d888093c4f33fef0" } } ], "extra": [ 1, 52, 217, 248, 47, 207, 232, 253, 123, 227, 13, 216, 242, 154, 169, 161, 167, 252, 105, 209, 71, 228, 107, 70, 49, 187, 74, 3, 175, 146, 221, 166, 136, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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