Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3eabdf642b460295752975dfaf170fbc21b6c82770e4d0c2395717f572c24ee

Tx prefix hash: 81e385041e88bb5b26423d1f8ed5f7d3ef9c1026117d0eaaf6b3f7281d8487da
Tx public key: d9767dfddbed607fb5ddf6f10816c96d0692d48b0fdd99cc8cefa9dab0c073e6
Timestamp: 1708479961 Timestamp [UCT]: 2024-02-21 01:46:01 Age [y:d:h:m:s]: 01:262:22:40:34
Block: 962050 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 446672 RingCT/type: yes/0
Extra: 01d9767dfddbed607fb5ddf6f10816c96d0692d48b0fdd99cc8cefa9dab0c073e602110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c81cebe3a7537447e0e97d9c445a8715e7d13287fe2c7f4ba5c31bbd15cd9940 0.600000000000 1421673 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": 962060, "vin": [ { "gen": { "height": 962050 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c81cebe3a7537447e0e97d9c445a8715e7d13287fe2c7f4ba5c31bbd15cd9940" } } ], "extra": [ 1, 217, 118, 125, 253, 219, 237, 96, 127, 181, 221, 246, 241, 8, 22, 201, 109, 6, 146, 212, 139, 15, 221, 153, 204, 140, 239, 169, 218, 176, 192, 115, 230, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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