Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d3bd712431378bb64e5cf9adefbf17edc8eb1d95c4b676b7500c41714c6daf9

Tx prefix hash: 8e48130bf917fcc3005a77785888e8a8d4d0054c385ea8a32c8328a0ae64d7ce
Tx public key: 5f1701341869c32f0bb6a8494ba3efb23a071d4bb7126c8388736c6177365383
Timestamp: 1698574210 Timestamp [UCT]: 2023-10-29 10:10:10 Age [y:d:h:m:s]: 01:152:09:33:20
Block: 880140 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369910 RingCT/type: yes/0
Extra: 015f1701341869c32f0bb6a8494ba3efb23a071d4bb7126c8388736c617736538302110000000275e3f0e9000000000000000000

1 output(s) for total of 0.744270540000 dcy

stealth address amount amount idx
00: 0543cee72417614a28d36399ea941aa432cf6de7963a318a4c9309261bc7ce4f 0.744270540000 1335686 of 0

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": 880150, "vin": [ { "gen": { "height": 880140 } } ], "vout": [ { "amount": 744270540, "target": { "key": "0543cee72417614a28d36399ea941aa432cf6de7963a318a4c9309261bc7ce4f" } } ], "extra": [ 1, 95, 23, 1, 52, 24, 105, 195, 47, 11, 182, 168, 73, 75, 163, 239, 178, 58, 7, 29, 75, 183, 18, 108, 131, 136, 115, 108, 97, 119, 54, 83, 131, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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