Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a218c918b85aafd53b7e5c664382398aa4afcaaba63b070418a492f20ece9b4

Tx prefix hash: 478bba845cbeebcefdf01d160987930499ace13fdec06060e9c0885b33d16f31
Tx public key: f908378cae0500aaeae530319092e3417618fc17d16e4c2a55377341ec563eb9
Timestamp: 1699041204 Timestamp [UCT]: 2023-11-03 19:53:24 Age [y:d:h:m:s]: 01:161:15:04:14
Block: 884003 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 376517 RingCT/type: yes/0
Extra: 01f908378cae0500aaeae530319092e3417618fc17d16e4c2a55377341ec563eb9021100000006e6d27f9c000000000000000000

1 output(s) for total of 0.722655148000 dcy

stealth address amount amount idx
00: e5da69c820d5f5c5571e2c3c172b8815b83b9ac92ea9080fa2f9647d91c03d71 0.722655148000 1339732 of 0

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": 884013, "vin": [ { "gen": { "height": 884003 } } ], "vout": [ { "amount": 722655148, "target": { "key": "e5da69c820d5f5c5571e2c3c172b8815b83b9ac92ea9080fa2f9647d91c03d71" } } ], "extra": [ 1, 249, 8, 55, 140, 174, 5, 0, 170, 234, 229, 48, 49, 144, 146, 227, 65, 118, 24, 252, 23, 209, 110, 76, 42, 85, 55, 115, 65, 236, 86, 62, 185, 2, 17, 0, 0, 0, 6, 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