Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 712d0c189b90a830307fab1ed881abfd1eeb064bea768b68ade965f6091d88f2

Tx prefix hash: 648e928202325117f2c1c35ef641c014440218106145c5e94dbff0a96a276f9c
Tx public key: e8d233fd64f3da870252edc6a39c9c362e55b1189f5d01ed240685934bcd5dde
Timestamp: 1702095551 Timestamp [UCT]: 2023-12-09 04:19:11 Age [y:d:h:m:s]: 01:161:05:39:38
Block: 909109 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376415 RingCT/type: yes/0
Extra: 01e8d233fd64f3da870252edc6a39c9c362e55b1189f5d01ed240685934bcd5dde021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9380065e439125e9bf211c9e845f72c93c613d855aae2fe21d63abcc1a64cffe 0.600000000000 1366174 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": 909119, "vin": [ { "gen": { "height": 909109 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9380065e439125e9bf211c9e845f72c93c613d855aae2fe21d63abcc1a64cffe" } } ], "extra": [ 1, 232, 210, 51, 253, 100, 243, 218, 135, 2, 82, 237, 198, 163, 156, 156, 54, 46, 85, 177, 24, 159, 93, 1, 237, 36, 6, 133, 147, 75, 205, 93, 222, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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