Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0646c89084c3a8753613be0bcee9363e1173dd6f97582e6a87f51bd6417ccd78

Tx prefix hash: 003d1b372a9bd5b8c8c6f66f96da28b690b0fa0b056533bfcdf27f5855877754
Tx public key: 09bb10e9fe12d3d0673655d4a8b67602ab8e5f0857e3708fbd0772d3b9c58eb6
Timestamp: 1718659463 Timestamp [UCT]: 2024-06-17 21:24:23 Age [y:d:h:m:s]: 00:208:08:10:39
Block: 1046441 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149089 RingCT/type: yes/0
Extra: 0109bb10e9fe12d3d0673655d4a8b67602ab8e5f0857e3708fbd0772d3b9c58eb602110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8c53e01773031ed0618c72e325907a83deceb2fa98f369b0f687179ae9138c7a 0.600000000000 1516254 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": 1046451, "vin": [ { "gen": { "height": 1046441 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8c53e01773031ed0618c72e325907a83deceb2fa98f369b0f687179ae9138c7a" } } ], "extra": [ 1, 9, 187, 16, 233, 254, 18, 211, 208, 103, 54, 85, 212, 168, 182, 118, 2, 171, 142, 95, 8, 87, 227, 112, 143, 189, 7, 114, 211, 185, 197, 142, 182, 2, 17, 0, 0, 0, 7, 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