Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21893e1b36d61361fd359270c2a3e359a1f6723c03867f754ecdb5f789b6002a

Tx prefix hash: 85250ccf14820cdeb534e8ed4af84f8e15e9dd0be8efb038a1fcaae36be847f6
Tx public key: e7479e1309e3d6bb8c2b1d9f38d9867aa8d6af6d6d5c3b4be86c8e2043913fac
Timestamp: 1674752707 Timestamp [UCT]: 2023-01-26 17:05:07 Age [y:d:h:m:s]: 02:119:20:26:53
Block: 683310 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 607341 RingCT/type: yes/0
Extra: 01e7479e1309e3d6bb8c2b1d9f38d9867aa8d6af6d6d5c3b4be86c8e2043913fac021100000001e6d27f9c000000000000000000

1 output(s) for total of 3.341259852000 dcy

stealth address amount amount idx
00: 27e61f023945a7e6dc443c9405003229ab04f8eb775c4228c46ffb5dca0bea61 3.341259852000 1125495 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": 683320, "vin": [ { "gen": { "height": 683310 } } ], "vout": [ { "amount": 3341259852, "target": { "key": "27e61f023945a7e6dc443c9405003229ab04f8eb775c4228c46ffb5dca0bea61" } } ], "extra": [ 1, 231, 71, 158, 19, 9, 227, 214, 187, 140, 43, 29, 159, 56, 217, 134, 122, 168, 214, 175, 109, 109, 92, 59, 75, 232, 108, 142, 32, 67, 145, 63, 172, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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