Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ec5f103ed424ca4d10c4b03f0b00948fd9b8e3edccc13ab3f76594201eb66f4

Tx prefix hash: 2e99d17bec41ed7f02a4d434d8105e20c6447723a55527879396bbe539e180de
Tx public key: 2fbdd223114ef0d786a93e305e14fec7c21fd4b70b8d39cc704a9374c9854aec
Timestamp: 1634623020 Timestamp [UCT]: 2021-10-19 05:57:00 Age [y:d:h:m:s]: 03:189:12:22:54
Block: 355980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 913342 RingCT/type: yes/0
Extra: 012fbdd223114ef0d786a93e305e14fec7c21fd4b70b8d39cc704a9374c9854aec02110000000f8d0de867000000000000000000

1 output(s) for total of 40.596715719000 dcy

stealth address amount amount idx
00: 0029f52edd8fd8b0e0b45199cb34aa3b081de558d629bbef63d1547253b2cbf8 40.596715719000 726514 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": 355990, "vin": [ { "gen": { "height": 355980 } } ], "vout": [ { "amount": 40596715719, "target": { "key": "0029f52edd8fd8b0e0b45199cb34aa3b081de558d629bbef63d1547253b2cbf8" } } ], "extra": [ 1, 47, 189, 210, 35, 17, 78, 240, 215, 134, 169, 62, 48, 94, 20, 254, 199, 194, 31, 212, 183, 11, 141, 57, 204, 112, 74, 147, 116, 201, 133, 74, 236, 2, 17, 0, 0, 0, 15, 141, 13, 232, 103, 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