Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0043bc7760b7363ec943a4307bc8b8c0d7c69bc8406510061d3f4daed914b49b

Tx prefix hash: eec4f33a642b0a4237a0886367f6b637cead6e26db1f9da4d0e0e5652d2e9c29
Tx public key: 67d4391335e2b17e9fd3d951cfb41dc194e871fb11c48dd55a4722f719a30504
Timestamp: 1727775950 Timestamp [UCT]: 2024-10-01 09:45:50 Age [y:d:h:m:s]: 00:113:21:03:19
Block: 1122027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81374 RingCT/type: yes/0
Extra: 0167d4391335e2b17e9fd3d951cfb41dc194e871fb11c48dd55a4722f719a30504021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7a6469cc4d3f36c8f955be6a26a8c08a09c9144c97f73aa30ef427bea5d33b5 0.600000000000 1604394 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": 1122037, "vin": [ { "gen": { "height": 1122027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7a6469cc4d3f36c8f955be6a26a8c08a09c9144c97f73aa30ef427bea5d33b5" } } ], "extra": [ 1, 103, 212, 57, 19, 53, 226, 177, 126, 159, 211, 217, 81, 207, 180, 29, 193, 148, 232, 113, 251, 17, 196, 141, 213, 90, 71, 34, 247, 25, 163, 5, 4, 2, 17, 0, 0, 0, 2, 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