Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91ecda571832c666134347b17375246bc4daea9a22fc3e69bf29f3e5af1dcafb

Tx prefix hash: 2a0b3782627a4fef53bd52c7ff8dac127179add8788be2c1426f680cab700613
Tx public key: 62de73fd0526ce112e4c15c8480f7b79045c1878b791d14767427402fe6ea3d3
Timestamp: 1639232937 Timestamp [UCT]: 2021-12-11 14:28:57 Age [y:d:h:m:s]: 02:342:08:04:10
Block: 393247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 762738 RingCT/type: yes/0
Extra: 0162de73fd0526ce112e4c15c8480f7b79045c1878b791d14767427402fe6ea3d3021100000001408d5ef5000000000000000000

1 output(s) for total of 30.549900896000 dcy

stealth address amount amount idx
00: e1625de78ca56863a5f4a7e5122da93d856d3a3129b3a3f41e6f5bcf6c7422fa 30.549900896000 790434 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": 393257, "vin": [ { "gen": { "height": 393247 } } ], "vout": [ { "amount": 30549900896, "target": { "key": "e1625de78ca56863a5f4a7e5122da93d856d3a3129b3a3f41e6f5bcf6c7422fa" } } ], "extra": [ 1, 98, 222, 115, 253, 5, 38, 206, 17, 46, 76, 21, 200, 72, 15, 123, 121, 4, 92, 24, 120, 183, 145, 209, 71, 103, 66, 116, 2, 254, 110, 163, 211, 2, 17, 0, 0, 0, 1, 64, 141, 94, 245, 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