Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6f821ab858c9862e3a78939dea10f3c2a79651a6094c3ff6a022d4e90dc14068

Tx prefix hash: 9faac9bdc1e714e8557b49916c95a972fa31119fb62e5d823571e8d5aaada5c3
Tx public key: 038aab1df77e1ecfb1abc16baf8f92cad12e4d4911f882408b46bfd3490560ca
Timestamp: 1737449178 Timestamp [UCT]: 2025-01-21 08:46:18 Age [y:d:h:m:s]: 00:150:19:42:36
Block: 1202025 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107487 RingCT/type: yes/0
Extra: 01038aab1df77e1ecfb1abc16baf8f92cad12e4d4911f882408b46bfd3490560ca0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e21cf539bfab3fe648fdac242f46f2d50d7bb79307243e2e7fab8159d80601b8 0.600000000000 1688684 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": 1202035, "vin": [ { "gen": { "height": 1202025 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e21cf539bfab3fe648fdac242f46f2d50d7bb79307243e2e7fab8159d80601b8" } } ], "extra": [ 1, 3, 138, 171, 29, 247, 126, 30, 207, 177, 171, 193, 107, 175, 143, 146, 202, 209, 46, 77, 73, 17, 248, 130, 64, 139, 70, 191, 211, 73, 5, 96, 202, 2, 17, 0, 0, 0, 2, 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