Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46d829ff4347df5fc75e64e7a4427b7da545ab052522159630b49b406d57ca52

Tx prefix hash: 693afe35ffd174d017b51b26a13c912c9544a80d5453b67f1caed8b7ed25f887
Tx public key: 8be416e8bdb9e8acb6c37b08434c432e9f6022e9efdc4b31b1989d694453dd3f
Timestamp: 1707961960 Timestamp [UCT]: 2024-02-15 01:52:40 Age [y:d:h:m:s]: 01:106:08:15:07
Block: 957745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337096 RingCT/type: yes/0
Extra: 018be416e8bdb9e8acb6c37b08434c432e9f6022e9efdc4b31b1989d694453dd3f0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a98c6609a9a03f9d8f1d7c5d8ac921a15920dcfe82486aeb955a7d4bb62621f4 0.600000000000 1417094 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": 957755, "vin": [ { "gen": { "height": 957745 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a98c6609a9a03f9d8f1d7c5d8ac921a15920dcfe82486aeb955a7d4bb62621f4" } } ], "extra": [ 1, 139, 228, 22, 232, 189, 185, 232, 172, 182, 195, 123, 8, 67, 76, 67, 46, 159, 96, 34, 233, 239, 220, 75, 49, 177, 152, 157, 105, 68, 83, 221, 63, 2, 17, 0, 0, 0, 5, 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