Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50e94f0a75604c2bea69e58cde9aad1de2d1d10fc75c449e67003824856a8872

Tx prefix hash: f7e9a4f35cd24b7ca60fa4ec96066da25a2e4b8ef95a92408c78131f704eb4e6
Tx public key: 4a3d3ab88fb200237edf28f8cbd62dd28b577411924da53a867283bfde1e9b6e
Timestamp: 1725807223 Timestamp [UCT]: 2024-09-08 14:53:43 Age [y:d:h:m:s]: 00:232:23:37:33
Block: 1105704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166379 RingCT/type: yes/0
Extra: 014a3d3ab88fb200237edf28f8cbd62dd28b577411924da53a867283bfde1e9b6e02110000000d91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbb0ca739d7b87623726e584f30332e0d160a4e5e937cd74bb7cfd221c3b38b1 0.600000000000 1583131 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": 1105714, "vin": [ { "gen": { "height": 1105704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbb0ca739d7b87623726e584f30332e0d160a4e5e937cd74bb7cfd221c3b38b1" } } ], "extra": [ 1, 74, 61, 58, 184, 143, 178, 0, 35, 126, 223, 40, 248, 203, 214, 45, 210, 139, 87, 116, 17, 146, 77, 165, 58, 134, 114, 131, 191, 222, 30, 155, 110, 2, 17, 0, 0, 0, 13, 145, 225, 60, 4, 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