Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efc3d3da0fa5388d5e3475ca76e57e6879188411f94c1b437a9bd85b846a6d1b

Tx prefix hash: fc3e87677e4f0b6a07161cfd1fe663c80dd85e01589f5e7a3ea437ef5e51531a
Tx public key: d81bc6433906c6fa6d092c7f9e5417865ba927fafae6c1729c541879f44d84c8
Timestamp: 1715554778 Timestamp [UCT]: 2024-05-12 22:59:38 Age [y:d:h:m:s]: 00:196:21:49:21
Block: 1020729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140918 RingCT/type: yes/0
Extra: 01d81bc6433906c6fa6d092c7f9e5417865ba927fafae6c1729c541879f44d84c80211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76d08c1f85b614907557e17071c5b920b657c5bacad047f7196899a82777c41f 0.600000000000 1484810 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": 1020739, "vin": [ { "gen": { "height": 1020729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76d08c1f85b614907557e17071c5b920b657c5bacad047f7196899a82777c41f" } } ], "extra": [ 1, 216, 27, 198, 67, 57, 6, 198, 250, 109, 9, 44, 127, 158, 84, 23, 134, 91, 169, 39, 250, 250, 230, 193, 114, 156, 84, 24, 121, 244, 77, 132, 200, 2, 17, 0, 0, 0, 2, 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