Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5a5ca18530f625a06edea8e02cac3d1650f573bb976efdb493faea7f927b6fa

Tx prefix hash: 304722482d94db7b96d3e9486bf089cbf529dfd90a775febadfcff0b15089a48
Tx public key: ac7f6dacd96b51038f524913cb46002dee1788525b99de8c4a7179b908ef9e0e
Timestamp: 1714257327 Timestamp [UCT]: 2024-04-27 22:35:27 Age [y:d:h:m:s]: 00:252:07:26:48
Block: 1009940 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180610 RingCT/type: yes/0
Extra: 01ac7f6dacd96b51038f524913cb46002dee1788525b99de8c4a7179b908ef9e0e02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc77346d1c5a8f6cf2e0bed249abe72ffda18fe04e3fc0e04ef9813d9c19993e 0.600000000000 1471754 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": 1009950, "vin": [ { "gen": { "height": 1009940 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc77346d1c5a8f6cf2e0bed249abe72ffda18fe04e3fc0e04ef9813d9c19993e" } } ], "extra": [ 1, 172, 127, 109, 172, 217, 107, 81, 3, 143, 82, 73, 19, 203, 70, 0, 45, 238, 23, 136, 82, 91, 153, 222, 140, 74, 113, 121, 185, 8, 239, 158, 14, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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