Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5e7201d0266a0ca60fb50cbc0d7e4e5fd35687a5eee0f84a4182998d4d0c4776

Tx prefix hash: b5c351676a41cadf4f6045cafe24634a28b8a9837d56791a410904fd597f0ccc
Tx public key: 16cbd012e3e5a82ac70d377c504decf58733e5053e39f15a0f177436ce1dc9da
Timestamp: 1703224159 Timestamp [UTC]: 2023-12-22 05:49:19 Age [y:d:h:m:s]: 02:065:14:42:32
Block: 918471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 566552 RingCT/type: yes/0
Extra: 0116cbd012e3e5a82ac70d377c504decf58733e5053e39f15a0f177436ce1dc9da0211000000020011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 1300401db83127f3f86fd2149f0c9afdecf42e1332295e2ae051ffac2d025205 0.000600000000 1376115 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 dinastycoin-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": 918481, "vin": [ { "gen": { "height": 918471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1300401db83127f3f86fd2149f0c9afdecf42e1332295e2ae051ffac2d025205" } } ], "extra": [ 1, 22, 203, 208, 18, 227, 229, 168, 42, 199, 13, 55, 124, 80, 77, 236, 245, 135, 51, 229, 5, 62, 57, 241, 90, 15, 23, 116, 54, 206, 29, 201, 218, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | dinastycoin version: tesla-369