Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d68bc54b6545ced778122f18aa9fa69b6ecd2aae2e962d18b6225835c7236e6

Tx prefix hash: 66a90008d50f2540650506dc51a7a92e1aad681239919aae73df2c64dc5d61c2
Tx public key: 2612485fefe85eaede4ef91d623a695cd474d6c45f6eaa82bf6f2c63ae969156
Timestamp: 1577318153 Timestamp [UCT]: 2019-12-25 23:55:53 Age [y:d:h:m:s]: 05:131:21:02:18
Block: 31734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1244098 RingCT/type: yes/0
Extra: 012612485fefe85eaede4ef91d623a695cd474d6c45f6eaa82bf6f2c63ae9691560211000000044ac5aa02000000000000000000

1 output(s) for total of 481.784633783000 dcy

stealth address amount amount idx
00: fd02c5a7e6ca68cca156d044765f2994af921a976070715ae54aa77cfe25f879 481.784633783000 52602 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": 31744, "vin": [ { "gen": { "height": 31734 } } ], "vout": [ { "amount": 481784633783, "target": { "key": "fd02c5a7e6ca68cca156d044765f2994af921a976070715ae54aa77cfe25f879" } } ], "extra": [ 1, 38, 18, 72, 95, 239, 232, 94, 174, 222, 78, 249, 29, 98, 58, 105, 92, 212, 116, 214, 196, 95, 110, 170, 130, 191, 111, 44, 99, 174, 150, 145, 86, 2, 17, 0, 0, 0, 4, 74, 197, 170, 2, 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