Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d18911513ac29b7d812ca00726e454778a1bf8d5c6a4ee1f3cb6041db5efe266

Tx prefix hash: 7e05737df849e4b17065fda4e46c3e781ca363ebbf499a2497432e5ef7a7a762
Tx public key: 8d679b82ae523de703e87c0d42459b37c892a46fdb337775fdb1687b7e06f5b0
Timestamp: 1703644502 Timestamp [UCT]: 2023-12-27 02:35:02 Age [y:d:h:m:s]: 01:140:16:57:06
Block: 921957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361703 RingCT/type: yes/0
Extra: 018d679b82ae523de703e87c0d42459b37c892a46fdb337775fdb1687b7e06f5b00211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8334711682a501b4990d5e6821f455223676cfb784f46ef77664d1cdf6030cfe 0.600000000000 1379651 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": 921967, "vin": [ { "gen": { "height": 921957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8334711682a501b4990d5e6821f455223676cfb784f46ef77664d1cdf6030cfe" } } ], "extra": [ 1, 141, 103, 155, 130, 174, 82, 61, 231, 3, 232, 124, 13, 66, 69, 155, 55, 200, 146, 164, 111, 219, 51, 119, 117, 253, 177, 104, 123, 126, 6, 245, 176, 2, 17, 0, 0, 0, 2, 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