Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7839f210ca54d1e1e0fcae7cedea3a3934e1517ed182f3c7eaa5dfc75262ef2c

Tx prefix hash: bd6299eb5bd22268e7c3db7921363c49c7e684c2dd3c385df18019a8859817a3
Tx public key: 3dc1161e6b4b0430497597a9c6c22bbdf63c2016157ec15a76914e75df6451c4
Timestamp: 1710656342 Timestamp [UCT]: 2024-03-17 06:19:02 Age [y:d:h:m:s]: 00:188:16:34:22
Block: 980120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135131 RingCT/type: yes/0
Extra: 013dc1161e6b4b0430497597a9c6c22bbdf63c2016157ec15a76914e75df6451c40211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25f8799aea383a5539ff84bc0f3c9dd976d73ea37164fe0ff66d20c9ace08541 0.600000000000 1440179 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": 980130, "vin": [ { "gen": { "height": 980120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25f8799aea383a5539ff84bc0f3c9dd976d73ea37164fe0ff66d20c9ace08541" } } ], "extra": [ 1, 61, 193, 22, 30, 107, 75, 4, 48, 73, 117, 151, 169, 198, 194, 43, 189, 246, 60, 32, 22, 21, 126, 193, 90, 118, 145, 78, 117, 223, 100, 81, 196, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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