Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a23dbe4efae09d5dc465efd9221d31e37f9886406ed4ba9396fd6b64680764c

Tx prefix hash: d2e89d95f6a8e381e342853686878c62170efc77929cb3c71e1a0da16e8b95de
Tx public key: 8d72387e7cb32f4edf573139493a59bd39572f7bde2cd7a3408250d16f8e0bd4
Timestamp: 1719932726 Timestamp [UCT]: 2024-07-02 15:05:26 Age [y:d:h:m:s]: 01:128:11:51:21
Block: 1057006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350358 RingCT/type: yes/0
Extra: 018d72387e7cb32f4edf573139493a59bd39572f7bde2cd7a3408250d16f8e0bd402110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7592f976e9eba135977d0e894a08d208b12406d4a017a25a9e7d071ca56d40b5 0.600000000000 1527435 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": 1057016, "vin": [ { "gen": { "height": 1057006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7592f976e9eba135977d0e894a08d208b12406d4a017a25a9e7d071ca56d40b5" } } ], "extra": [ 1, 141, 114, 56, 126, 124, 179, 47, 78, 223, 87, 49, 57, 73, 58, 89, 189, 57, 87, 47, 123, 222, 44, 215, 163, 64, 130, 80, 209, 111, 142, 11, 212, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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