Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a648e30a02266b49f9fe707a50f3b2f80efffcb4f597ed552bfd10a7691bab85

Tx prefix hash: 898f7db6983198881d5de845011e15ae8a23390de882127f2e17d032c9a9b856
Tx public key: 2d242cad5d95a55a5caa04a9e21f2d20e74ffa3f40928bc75af08c6099ad88d7
Timestamp: 1707767008 Timestamp [UCT]: 2024-02-12 19:43:28 Age [y:d:h:m:s]: 01:127:01:36:33
Block: 956137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 351766 RingCT/type: yes/0
Extra: 012d242cad5d95a55a5caa04a9e21f2d20e74ffa3f40928bc75af08c6099ad88d702110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f473f29158c3584e57cb8d90d48c113db792e48c413e984ea935190c90f54b6 0.600000000000 1415439 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": 956147, "vin": [ { "gen": { "height": 956137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f473f29158c3584e57cb8d90d48c113db792e48c413e984ea935190c90f54b6" } } ], "extra": [ 1, 45, 36, 44, 173, 93, 149, 165, 90, 92, 170, 4, 169, 226, 31, 45, 32, 231, 79, 250, 63, 64, 146, 139, 199, 90, 240, 140, 96, 153, 173, 136, 215, 2, 17, 0, 0, 0, 8, 82, 212, 126, 148, 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