Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3e61cb71c8504806423622c68efbf38f8a5cb4d742f1aa428afd666b610af6eb

Tx prefix hash: 6e6425cd338c352842a273532fa29378387081f37b96037e154d6219d5e054e8
Tx public key: fdd6e953f9168dfe4557eae14cba7f7d66924f3dca70246267be96d8432c22d3
Timestamp: 1577983065 Timestamp [UCT]: 2020-01-02 16:37:45 Age [y:d:h:m:s]: 05:004:11:01:44
Block: 37332 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1153145 RingCT/type: yes/0
Extra: 01fdd6e953f9168dfe4557eae14cba7f7d66924f3dca70246267be96d8432c22d3021100000008d81c26c0000000000000000000

1 output(s) for total of 461.641069278000 dcy

stealth address amount amount idx
00: 92d57c50c14f265df1631551dd3c167e7ddb43686c69db06ea93b54d8a5562bf 461.641069278000 63324 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": 37342, "vin": [ { "gen": { "height": 37332 } } ], "vout": [ { "amount": 461641069278, "target": { "key": "92d57c50c14f265df1631551dd3c167e7ddb43686c69db06ea93b54d8a5562bf" } } ], "extra": [ 1, 253, 214, 233, 83, 249, 22, 141, 254, 69, 87, 234, 225, 76, 186, 127, 125, 102, 146, 79, 61, 202, 112, 36, 98, 103, 190, 150, 216, 67, 44, 34, 211, 2, 17, 0, 0, 0, 8, 216, 28, 38, 192, 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