Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2b756b0a8ca45439667698a38b2fefd238532347ed1f8dca006eeb49ea8f3b6

Tx prefix hash: a6e519c4c83f2d359b115eb010409b2ac2fd16e9cae2739abd692c899418f158
Tx public key: 4190767d7d36a1f564ed53202a15b1c9d151a38b90ceef5bddaac03e9a698083
Timestamp: 1702394006 Timestamp [UCT]: 2023-12-12 15:13:26 Age [y:d:h:m:s]: 01:184:12:59:06
Block: 911610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392975 RingCT/type: yes/0
Extra: 014190767d7d36a1f564ed53202a15b1c9d151a38b90ceef5bddaac03e9a698083021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0cdf39e3fc9d2a769e954074b3c05ad5d79cb04143b370be468399ce0f076998 0.600000000000 1368824 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": 911620, "vin": [ { "gen": { "height": 911610 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0cdf39e3fc9d2a769e954074b3c05ad5d79cb04143b370be468399ce0f076998" } } ], "extra": [ 1, 65, 144, 118, 125, 125, 54, 161, 245, 100, 237, 83, 32, 42, 21, 177, 201, 209, 81, 163, 139, 144, 206, 239, 91, 221, 170, 192, 62, 154, 105, 128, 131, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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