Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8ccfab67227cb0dc037050e8ed88a45079d74f9d7d950d7ca05a7f27e2c11d9

Tx prefix hash: 8ccd69cd928580708f7e16f53bd03a61598c5fccfc8f71feba533f49f2733e46
Tx public key: c621783b297b629e6812d0f45bf0fc0ac9ba2685e90c9abacfabf648e5054763
Timestamp: 1729347016 Timestamp [UCT]: 2024-10-19 14:10:16 Age [y:d:h:m:s]: 00:175:04:28:11
Block: 1135041 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124986 RingCT/type: yes/0
Extra: 01c621783b297b629e6812d0f45bf0fc0ac9ba2685e90c9abacfabf648e5054763021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbaee6d7e5f610ed6fee7a2302ad22f6f34b09152a64a2ea7e46584781b04cda 0.600000000000 1618370 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": 1135051, "vin": [ { "gen": { "height": 1135041 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbaee6d7e5f610ed6fee7a2302ad22f6f34b09152a64a2ea7e46584781b04cda" } } ], "extra": [ 1, 198, 33, 120, 59, 41, 123, 98, 158, 104, 18, 208, 244, 91, 240, 252, 10, 201, 186, 38, 133, 233, 12, 154, 186, 207, 171, 246, 72, 229, 5, 71, 99, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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