Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5aef76a6d1a9e0013797f688e2575efe7543af885e28fc6362f4a18607ee4b0

Tx prefix hash: a8684b0282cd03b2297c1e7dab83743cbeddacca4568c5aaec29598bc81b21c2
Tx public key: 2a714860f93562d8a3f5c47cdbd91ba8945dd56e9678dcb00e1c3496d91fa09e
Timestamp: 1727888162 Timestamp [UCT]: 2024-10-02 16:56:02 Age [y:d:h:m:s]: 00:162:22:41:15
Block: 1122961 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 116256 RingCT/type: yes/0
Extra: 012a714860f93562d8a3f5c47cdbd91ba8945dd56e9678dcb00e1c3496d91fa09e021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: afe1a5bef6db734b822e7f377a2362785adba5f9f5ddd8a62cd424e7db22e2ae 0.600000000000 1605494 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": 1122971, "vin": [ { "gen": { "height": 1122961 } } ], "vout": [ { "amount": 600000000, "target": { "key": "afe1a5bef6db734b822e7f377a2362785adba5f9f5ddd8a62cd424e7db22e2ae" } } ], "extra": [ 1, 42, 113, 72, 96, 249, 53, 98, 216, 163, 245, 196, 124, 219, 217, 27, 168, 148, 93, 213, 110, 150, 120, 220, 176, 14, 28, 52, 150, 217, 31, 160, 158, 2, 17, 0, 0, 0, 1, 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