Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1643f3037ebead2bd334b438d14b5d332be1c3a86576b227d2494eb3b9936c78

Tx prefix hash: da863bd692bc726e7afe8d4add8878e411b798e3a3e4d1bc9bdd710546e86810
Tx public key: 67715aedb54be8207e1c3178b089f578fbba2aae164a831d7a33f0a01b0c3956
Timestamp: 1702736586 Timestamp [UCT]: 2023-12-16 14:23:06 Age [y:d:h:m:s]: 01:322:01:55:59
Block: 914428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489031 RingCT/type: yes/0
Extra: 0167715aedb54be8207e1c3178b089f578fbba2aae164a831d7a33f0a01b0c3956021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c11b3f4a28e05f5f664f55c6512462b3379eca0ef996a8a830f00ad72169c839 0.600000000000 1371744 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": 914438, "vin": [ { "gen": { "height": 914428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c11b3f4a28e05f5f664f55c6512462b3379eca0ef996a8a830f00ad72169c839" } } ], "extra": [ 1, 103, 113, 90, 237, 181, 75, 232, 32, 126, 28, 49, 120, 176, 137, 245, 120, 251, 186, 42, 174, 22, 74, 131, 29, 122, 51, 240, 160, 27, 12, 57, 86, 2, 17, 0, 0, 0, 1, 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