Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93ee3b4a1afece2090336827c590611421c86b2b8e6552f3d3abad737fca5732

Tx prefix hash: 8276671fa05734b08351f4df1e90d9d0a6627d882d732b7c108f9cf8d14ba4fd
Tx public key: 4d5ffe178e165e5b8df76f3854273b34eb6c2fe9b36127a030e62aad98c4055c
Timestamp: 1732014239 Timestamp [UCT]: 2024-11-19 11:03:59 Age [y:d:h:m:s]: 00:216:12:16:29
Block: 1157067 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154357 RingCT/type: yes/0
Extra: 014d5ffe178e165e5b8df76f3854273b34eb6c2fe9b36127a030e62aad98c4055c0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a7ce1debc4714e9a1ae1308c1886fd98a1b58ad275b7d211c2303c0bddc63b2 0.600000000000 1642690 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": 1157077, "vin": [ { "gen": { "height": 1157067 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a7ce1debc4714e9a1ae1308c1886fd98a1b58ad275b7d211c2303c0bddc63b2" } } ], "extra": [ 1, 77, 95, 254, 23, 142, 22, 94, 91, 141, 247, 111, 56, 84, 39, 59, 52, 235, 108, 47, 233, 179, 97, 39, 160, 48, 230, 42, 173, 152, 196, 5, 92, 2, 17, 0, 0, 0, 3, 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