Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee7eea1643b206fa08f7a0e6de3cdde21cbfce3d7c0cefb6b8ec7f06cccb4f8c

Tx prefix hash: 3369c8089c066b766f1d075c28d92d3f1caba60605348d94021f0fa7c442c07f
Tx public key: 8fa802e03ab1881250a4b082d9a2c851b40c62129439070d9793a825a9d3c5cc
Timestamp: 1707440104 Timestamp [UCT]: 2024-02-09 00:55:04 Age [y:d:h:m:s]: 01:058:21:19:27
Block: 953413 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303130 RingCT/type: yes/0
Extra: 018fa802e03ab1881250a4b082d9a2c851b40c62129439070d9793a825a9d3c5cc02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3850994fbc2d5e1abaf6e18c6ef0fded4e8929932d0cd4ac616c6e1afcf0cd91 0.600000000000 1412615 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": 953423, "vin": [ { "gen": { "height": 953413 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3850994fbc2d5e1abaf6e18c6ef0fded4e8929932d0cd4ac616c6e1afcf0cd91" } } ], "extra": [ 1, 143, 168, 2, 224, 58, 177, 136, 18, 80, 164, 176, 130, 217, 162, 200, 81, 180, 12, 98, 18, 148, 57, 7, 13, 151, 147, 168, 37, 169, 211, 197, 204, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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