Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8525b35225cd5f050498d45414f94cb1182a9004c5d4c0001d0b9902e56317ce

Tx prefix hash: 9f385c3f92544af330e15877c6283c55f444dc378a6ac2b2f6e315ac3361bbd5
Tx public key: a24d41aefbfd923f9c920ee2fa8ee9609f8d6934dd8994e335261dd37e7e915b
Timestamp: 1712091631 Timestamp [UCT]: 2024-04-02 21:00:31 Age [y:d:h:m:s]: 00:296:14:17:32
Block: 991962 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212280 RingCT/type: yes/0
Extra: 01a24d41aefbfd923f9c920ee2fa8ee9609f8d6934dd8994e335261dd37e7e915b0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0c88ee9c042fa77b47229f1d3e89fdeadb747efefa3867d4d86ee534f0cbb936 0.600000000000 1452298 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": 991972, "vin": [ { "gen": { "height": 991962 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0c88ee9c042fa77b47229f1d3e89fdeadb747efefa3867d4d86ee534f0cbb936" } } ], "extra": [ 1, 162, 77, 65, 174, 251, 253, 146, 63, 156, 146, 14, 226, 250, 142, 233, 96, 159, 141, 105, 52, 221, 137, 148, 227, 53, 38, 29, 211, 126, 126, 145, 91, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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