Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a29f9eff5a51efb604286624fe73df6f8fd7d3741ed8f3331edecdfc1d76bd9b

Tx prefix hash: c2ebc6dcb73f6661fa4ae752d9ae431dcb6d959c25b6d4bedde79d8312ae391a
Tx public key: 1f5b9b9fdc793d56090d43947e32d49e6d2f717190db59726d76e3cf19044089
Timestamp: 1636936375 Timestamp [UCT]: 2021-11-15 00:32:55 Age [y:d:h:m:s]: 03:087:04:21:52
Block: 374468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 840815 RingCT/type: yes/0
Extra: 011f5b9b9fdc793d56090d43947e32d49e6d2f717190db59726d76e3cf1904408902110000000ad6e4826b000000000000000000

1 output(s) for total of 35.255952687000 dcy

stealth address amount amount idx
00: cf841f6dc919c6aeb1a18913e59d1e05baf36bf75d2d5d326892f87636e697f1 35.255952687000 757964 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": 374478, "vin": [ { "gen": { "height": 374468 } } ], "vout": [ { "amount": 35255952687, "target": { "key": "cf841f6dc919c6aeb1a18913e59d1e05baf36bf75d2d5d326892f87636e697f1" } } ], "extra": [ 1, 31, 91, 155, 159, 220, 121, 61, 86, 9, 13, 67, 148, 126, 50, 212, 158, 109, 47, 113, 113, 144, 219, 89, 114, 109, 118, 227, 207, 25, 4, 64, 137, 2, 17, 0, 0, 0, 10, 214, 228, 130, 107, 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