Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88279dc8e6780a8cae201f6c6202b2bc3544a1afc4706177932faed983238ad8

Tx prefix hash: 54b8e71b1ccc9e959cf2b3a9b57771c78b3ecd73be2f0122c470f4683db14df1
Tx public key: 8cf5cfc44c6c2ee152c4d0a8081a23edbe99caf9a2ede31868c71d51e1e09435
Timestamp: 1736314802 Timestamp [UCT]: 2025-01-08 05:40:02 Age [y:d:h:m:s]: 00:082:00:40:41
Block: 1192670 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 58404 RingCT/type: yes/0
Extra: 018cf5cfc44c6c2ee152c4d0a8081a23edbe99caf9a2ede31868c71d51e1e094350211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea22cb35af4dc9c19e993334830482f4fd9c40d73cff2fc250e508dd52686367 0.600000000000 1679225 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": 1192680, "vin": [ { "gen": { "height": 1192670 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea22cb35af4dc9c19e993334830482f4fd9c40d73cff2fc250e508dd52686367" } } ], "extra": [ 1, 140, 245, 207, 196, 76, 108, 46, 225, 82, 196, 208, 168, 8, 26, 35, 237, 190, 153, 202, 249, 162, 237, 227, 24, 104, 199, 29, 81, 225, 224, 148, 53, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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