Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8be70451c79f12f19510902c63c18f78be55ea57015e38b22a5aa28f7325c77

Tx prefix hash: 8d27fac1ccaf81ae9a2faac3dfd36764a5194204fd9603c90912f9dc76c7ebc5
Tx public key: 47f262ecaa1df86f6967f5f97e33289061ea8c2fdbb4235a75391eb88125dc97
Timestamp: 1711441957 Timestamp [UCT]: 2024-03-26 08:32:37 Age [y:d:h:m:s]: 00:299:05:14:05
Block: 986629 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214114 RingCT/type: yes/0
Extra: 0147f262ecaa1df86f6967f5f97e33289061ea8c2fdbb4235a75391eb88125dc970211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3f2712916215b455b049b21af027e532e90352b5660b8c2f3710d1c915aa16c 0.600000000000 1446860 of 15

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": 986639, "vin": [ { "gen": { "height": 986629 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3f2712916215b455b049b21af027e532e90352b5660b8c2f3710d1c915aa16c" } } ], "extra": [ 1, 71, 242, 98, 236, 170, 29, 248, 111, 105, 103, 245, 249, 126, 51, 40, 144, 97, 234, 140, 47, 219, 180, 35, 90, 117, 57, 30, 184, 129, 37, 220, 151, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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