Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2d1eda2dbc11367e2489b4346d3882a00f2794b9230b1a6a4e22fb4551787c6

Tx prefix hash: 8fbcf5296039f313ded3a43f98835b4fccc06f100e06d717bce0d38e6c626026
Tx public key: e441a713a389240d3d87d6dcfae3520467ea479810f03ee3c8391237e6f1771e
Timestamp: 1703492791 Timestamp [UCT]: 2023-12-25 08:26:31 Age [y:d:h:m:s]: 01:324:05:08:26
Block: 920704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490555 RingCT/type: yes/0
Extra: 01e441a713a389240d3d87d6dcfae3520467ea479810f03ee3c8391237e6f1771e021100000006ad5694ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe753b041393fdbdfb0f54e685acb6902aac75025829b95c5c047055ee6f254e 0.600000000000 1378386 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": 920714, "vin": [ { "gen": { "height": 920704 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe753b041393fdbdfb0f54e685acb6902aac75025829b95c5c047055ee6f254e" } } ], "extra": [ 1, 228, 65, 167, 19, 163, 137, 36, 13, 61, 135, 214, 220, 250, 227, 82, 4, 103, 234, 71, 152, 16, 240, 62, 227, 200, 57, 18, 55, 230, 241, 119, 30, 2, 17, 0, 0, 0, 6, 173, 86, 148, 172, 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