Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2212254a02991a48b987bd4aba4fbad4fc014c8217d7991e71820edcba16d894

Tx prefix hash: 3978cfb52aeec01eccf3a7a2cdd4ce24b32cf10e50bdfc7146179640b629c0b4
Tx public key: dfcdc5086025e33f69d3cb9e4e06835c65d9a98589839e3c0759ef3f43d21080
Timestamp: 1726203270 Timestamp [UCT]: 2024-09-13 04:54:30 Age [y:d:h:m:s]: 00:163:05:35:20
Block: 1108976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116465 RingCT/type: yes/0
Extra: 01dfcdc5086025e33f69d3cb9e4e06835c65d9a98589839e3c0759ef3f43d21080021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd2ac1cb4909b425fe111047d832ac32654441a3110429a610b4443862bb1ff0 0.600000000000 1587065 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": 1108986, "vin": [ { "gen": { "height": 1108976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd2ac1cb4909b425fe111047d832ac32654441a3110429a610b4443862bb1ff0" } } ], "extra": [ 1, 223, 205, 197, 8, 96, 37, 227, 63, 105, 211, 203, 158, 78, 6, 131, 92, 101, 217, 169, 133, 137, 131, 158, 60, 7, 89, 239, 63, 67, 210, 16, 128, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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