Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a4f796448f94691e49b00459fe9dfb9e116c0c6425f357d0695ff721974ae22

Tx prefix hash: e44497efbe00ce3c53f406b290a1a2d05c6c15ee670e88ccc9409f4650413a11
Tx public key: c8d6c9aff0a6103b06e3763696d2401c8dc7d3b7e063dbe5c5641aaef65265e4
Timestamp: 1580267677 Timestamp [UCT]: 2020-01-29 03:14:37 Age [y:d:h:m:s]: 04:302:17:31:15
Block: 54712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1106935 RingCT/type: yes/0
Extra: 01c8d6c9aff0a6103b06e3763696d2401c8dc7d3b7e063dbe5c5641aaef65265e402110000001bdcee4b4d000000000000000000

1 output(s) for total of 404.312583379000 dcy

stealth address amount amount idx
00: 475c1d7989ff8ee1bb10634b940f98ba4d77e401d2308c6b76cc5f90cd0ef3aa 404.312583379000 101178 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": 54722, "vin": [ { "gen": { "height": 54712 } } ], "vout": [ { "amount": 404312583379, "target": { "key": "475c1d7989ff8ee1bb10634b940f98ba4d77e401d2308c6b76cc5f90cd0ef3aa" } } ], "extra": [ 1, 200, 214, 201, 175, 240, 166, 16, 59, 6, 227, 118, 54, 150, 210, 64, 28, 141, 199, 211, 183, 224, 99, 219, 229, 197, 100, 26, 174, 246, 82, 101, 228, 2, 17, 0, 0, 0, 27, 220, 238, 75, 77, 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