Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e882eba7313225f9477b9e0bce27f6ed98ff53fff81ab7e48404913ae05501b6

Tx prefix hash: a18a9ad212476fe1d61be74038d8142f6f4c95df784a163493897e5fd370856b
Tx public key: b2db7048d8f876e9150c3cfd963d4ec186d57e8c2a2652b25c2d0c98aa0920ad
Timestamp: 1665372502 Timestamp [UCT]: 2022-10-10 03:28:22 Age [y:d:h:m:s]: 02:040:07:16:20
Block: 605784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 550559 RingCT/type: yes/0
Extra: 01b2db7048d8f876e9150c3cfd963d4ec186d57e8c2a2652b25c2d0c98aa0920ad021100000004272bcc39000000000000000000

1 output(s) for total of 6.036513642000 dcy

stealth address amount amount idx
00: 1db99995b81ca809348bfaf8c496f1a472a7e33b2a56ea5a7c39b5d43c0ba5ab 6.036513642000 1042211 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": 605794, "vin": [ { "gen": { "height": 605784 } } ], "vout": [ { "amount": 6036513642, "target": { "key": "1db99995b81ca809348bfaf8c496f1a472a7e33b2a56ea5a7c39b5d43c0ba5ab" } } ], "extra": [ 1, 178, 219, 112, 72, 216, 248, 118, 233, 21, 12, 60, 253, 150, 61, 78, 193, 134, 213, 126, 140, 42, 38, 82, 178, 92, 45, 12, 152, 170, 9, 32, 173, 2, 17, 0, 0, 0, 4, 39, 43, 204, 57, 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