Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5d04ae28e994dcf56b8e55d82d2eb9a3fade4ee79ab9637d80d99dbf48bd31f

Tx prefix hash: a6487162d991e2495399890ba4f7c894b690834e5d08a3e4a02862a16dbbb161
Tx public key: 98e3ca7e401bb39a5e5daaaab50c8cbe17731beff92dcd3b86bbb1faa83b43f9
Timestamp: 1676529373 Timestamp [UCT]: 2023-02-16 06:36:13 Age [y:d:h:m:s]: 02:056:13:54:34
Block: 698050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 562033 RingCT/type: yes/0
Extra: 0198e3ca7e401bb39a5e5daaaab50c8cbe17731beff92dcd3b86bbb1faa83b43f9021100000003835e4d22000000000000000000

1 output(s) for total of 2.985867226000 dcy

stealth address amount amount idx
00: 0751d38583967c96d0c753fee55cbac1685d5e90702eca793e1589ce453a37d4 2.985867226000 1141315 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": 698060, "vin": [ { "gen": { "height": 698050 } } ], "vout": [ { "amount": 2985867226, "target": { "key": "0751d38583967c96d0c753fee55cbac1685d5e90702eca793e1589ce453a37d4" } } ], "extra": [ 1, 152, 227, 202, 126, 64, 27, 179, 154, 94, 93, 170, 170, 181, 12, 140, 190, 23, 115, 27, 239, 249, 45, 205, 59, 134, 187, 177, 250, 168, 59, 67, 249, 2, 17, 0, 0, 0, 3, 131, 94, 77, 34, 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