Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28e0c4c686938abf2283268a3020af273f380d51bbd9afbb862b4aaf16f34d42

Tx prefix hash: 2898a190e5201e9f0de778ce8193511403b202139083d9b6b5395079116fe55c
Tx public key: aa7f376c92253d6a2a354d390839a19d72ff4a838575614239612d3a85e86b46
Timestamp: 1719544563 Timestamp [UCT]: 2024-06-28 03:16:03 Age [y:d:h:m:s]: 00:334:17:06:06
Block: 1053775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239224 RingCT/type: yes/0
Extra: 01aa7f376c92253d6a2a354d390839a19d72ff4a838575614239612d3a85e86b460211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc789702d56b036ed47a1a1ab4ce492089e99b97114851bd9f74f0b868b49c18 0.600000000000 1524126 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": 1053785, "vin": [ { "gen": { "height": 1053775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc789702d56b036ed47a1a1ab4ce492089e99b97114851bd9f74f0b868b49c18" } } ], "extra": [ 1, 170, 127, 55, 108, 146, 37, 61, 106, 42, 53, 77, 57, 8, 57, 161, 157, 114, 255, 74, 131, 133, 117, 97, 66, 57, 97, 45, 58, 133, 232, 107, 70, 2, 17, 0, 0, 0, 3, 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