Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95e0e8cece5e4def039b33fe2416de7f8a349debd10b7813a70f08ff070c49ee

Tx prefix hash: c3aa18dc99fcd30c34cad98fc8563cfb0902a25e74b9d499dcf7e61a723a1f91
Tx public key: 8c2df897cd49f34dd25b8754c542887e6efe519115fdab843e4b9eee40b868ce
Timestamp: 1715515996 Timestamp [UCT]: 2024-05-12 12:13:16 Age [y:d:h:m:s]: 00:227:03:15:17
Block: 1020412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 162547 RingCT/type: yes/0
Extra: 018c2df897cd49f34dd25b8754c542887e6efe519115fdab843e4b9eee40b868ce021100000002c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c4434f64d841f11c0299c2903c4d37af9d2051d0c565a269842289b72d90b343 0.600000000000 1484483 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": 1020422, "vin": [ { "gen": { "height": 1020412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c4434f64d841f11c0299c2903c4d37af9d2051d0c565a269842289b72d90b343" } } ], "extra": [ 1, 140, 45, 248, 151, 205, 73, 243, 77, 210, 91, 135, 84, 197, 66, 136, 126, 110, 254, 81, 145, 21, 253, 171, 132, 62, 75, 158, 238, 64, 184, 104, 206, 2, 17, 0, 0, 0, 2, 197, 69, 41, 96, 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