Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 42ee25db8733c6db9feb6435e94e0754c69c33ce1737f4fe248d4771a3617a18

Tx prefix hash: 6abfcc5132b6500c97193e73de8e488c8a2d4a29c1e8305bf31cf1983654abae
Tx public key: e5f5be5788e0f0dc8f3dfd60553cf606fcbe17e89cfa24e1a22277b0babb6c9f
Timestamp: 1584027657 Timestamp [UCT]: 2020-03-12 15:40:57 Age [y:d:h:m:s]: 04:333:21:24:52
Block: 81309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1133502 RingCT/type: yes/0
Extra: 01e5f5be5788e0f0dc8f3dfd60553cf606fcbe17e89cfa24e1a22277b0babb6c9f0211000000104ac5aa02000000000000000000

1 output(s) for total of 330.058041299000 dcy

stealth address amount amount idx
00: 242f5f4fb5d0f64d3e0ee1f39c3ae5f459012bcf9fbf1a1089ad17aedbf40059 330.058041299000 148599 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": 81319, "vin": [ { "gen": { "height": 81309 } } ], "vout": [ { "amount": 330058041299, "target": { "key": "242f5f4fb5d0f64d3e0ee1f39c3ae5f459012bcf9fbf1a1089ad17aedbf40059" } } ], "extra": [ 1, 229, 245, 190, 87, 136, 224, 240, 220, 143, 61, 253, 96, 85, 60, 246, 6, 252, 190, 23, 232, 156, 250, 36, 225, 162, 34, 119, 176, 186, 187, 108, 159, 2, 17, 0, 0, 0, 16, 74, 197, 170, 2, 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