Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfdfbf48a5ce13fe782fef54a262593ff792a12b85d574c976b0c71fa9889efc

Tx prefix hash: 91d87208a71feb721ac902538bd7f33ca43857994b90fc0ca54804c0cd0a3918
Tx public key: acc39cfd9f2d2eae7f89469b702405ed00fdca44b95265617d7c5325a00d9ae3
Timestamp: 1718073333 Timestamp [UCT]: 2024-06-11 02:35:33 Age [y:d:h:m:s]: 00:166:20:17:52
Block: 1041590 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119409 RingCT/type: yes/0
Extra: 01acc39cfd9f2d2eae7f89469b702405ed00fdca44b95265617d7c5325a00d9ae30211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 445694f34ece09f9ca1ca329229058e7bc38eb8af73a4a429b03d97ffdb0cb61 0.600000000000 1510299 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": 1041600, "vin": [ { "gen": { "height": 1041590 } } ], "vout": [ { "amount": 600000000, "target": { "key": "445694f34ece09f9ca1ca329229058e7bc38eb8af73a4a429b03d97ffdb0cb61" } } ], "extra": [ 1, 172, 195, 156, 253, 159, 45, 46, 174, 127, 137, 70, 155, 112, 36, 5, 237, 0, 253, 202, 68, 185, 82, 101, 97, 125, 124, 83, 37, 160, 13, 154, 227, 2, 17, 0, 0, 0, 1, 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