Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9047c43dc1af78bbd881d6504c76ffe563dad7d99c8195ad515b8d21fe0fd6ab

Tx prefix hash: 4af73ee8625780d473c8ef7d9edf7b91c0e30f34b3e0baab87dc1383e5da0336
Tx public key: 79a000c18b97aa3b2ca7c9dc10d670d06a490d0a0ffd33386376ee81ab22eb68
Timestamp: 1709001600 Timestamp [UCT]: 2024-02-27 02:40:00 Age [y:d:h:m:s]: 01:281:21:58:00
Block: 966381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460261 RingCT/type: yes/0
Extra: 0179a000c18b97aa3b2ca7c9dc10d670d06a490d0a0ffd33386376ee81ab22eb680211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d26bc0dd924528a9ff3539ac39301a79f8889f97f7239d529e593aa5a29f9751 0.600000000000 1426138 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": 966391, "vin": [ { "gen": { "height": 966381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d26bc0dd924528a9ff3539ac39301a79f8889f97f7239d529e593aa5a29f9751" } } ], "extra": [ 1, 121, 160, 0, 193, 139, 151, 170, 59, 44, 167, 201, 220, 16, 214, 112, 208, 106, 73, 13, 10, 15, 253, 51, 56, 99, 118, 238, 129, 171, 34, 235, 104, 2, 17, 0, 0, 0, 8, 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