Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5649035459176860dc5a8c35ff31448ac566e54345f90f34b2e1dde37ae38d57

Tx prefix hash: 28f67e5acb8704363a5d32c2b488eefda4611617d4f7d984780274094cdb5333
Tx public key: 6dc3b29a2e60f0241b683ff02b9d830f8ecb248485ac1f53f1e6307636136e4a
Timestamp: 1723480750 Timestamp [UCT]: 2024-08-12 16:39:10 Age [y:d:h:m:s]: 00:245:16:57:20
Block: 1086413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175496 RingCT/type: yes/0
Extra: 016dc3b29a2e60f0241b683ff02b9d830f8ecb248485ac1f53f1e6307636136e4a021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2752ed575e8ca706f007963d863fce4ba0ea5efbfc9de0f4dfff9b8c1298073a 0.600000000000 1561010 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": 1086423, "vin": [ { "gen": { "height": 1086413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2752ed575e8ca706f007963d863fce4ba0ea5efbfc9de0f4dfff9b8c1298073a" } } ], "extra": [ 1, 109, 195, 178, 154, 46, 96, 240, 36, 27, 104, 63, 240, 43, 157, 131, 15, 142, 203, 36, 132, 133, 172, 31, 83, 241, 230, 48, 118, 54, 19, 110, 74, 2, 17, 0, 0, 0, 7, 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