Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e35771ecd72d7d98cbdf6123de04d6f2d2546305a2d511acbd9a0c7a20ff04b6

Tx prefix hash: 59d396702fd5db220b5f9d2c5906362394f360a9f1ade63d8e9879938e116b72
Tx public key: d231ef1569e7f3ec677132cec8d663bc65fef9f2aa8272db7cf8fa528e17f371
Timestamp: 1673111737 Timestamp [UCT]: 2023-01-07 17:15:37 Age [y:d:h:m:s]: 02:127:10:49:27
Block: 669685 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 612802 RingCT/type: yes/0
Extra: 01d231ef1569e7f3ec677132cec8d663bc65fef9f2aa8272db7cf8fa528e17f37102110000000152542ceb000000000000000000

1 output(s) for total of 3.707281408000 dcy

stealth address amount amount idx
00: 7893529031fc73558dde4c5d36211135da0ee5c31e65253354d9dc3a1b2f7f15 3.707281408000 1111038 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": 669695, "vin": [ { "gen": { "height": 669685 } } ], "vout": [ { "amount": 3707281408, "target": { "key": "7893529031fc73558dde4c5d36211135da0ee5c31e65253354d9dc3a1b2f7f15" } } ], "extra": [ 1, 210, 49, 239, 21, 105, 231, 243, 236, 103, 113, 50, 206, 200, 214, 99, 188, 101, 254, 249, 242, 170, 130, 114, 219, 124, 248, 250, 82, 142, 23, 243, 113, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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