Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c01fe41e82cc42f5554253464454b002487a3b9c3c141c13934d41b9ec0fefa

Tx prefix hash: 2eaf7b2fc61dc8e76932a2f3f4d965bcb90730dff2d580a9d9ec1bc6c3577c8c
Tx public key: 7a96cda2ca3c51788c70cac4ffc6351bfd0c4441d9064dca81c0cf5d78c4c510
Timestamp: 1685095252 Timestamp [UCT]: 2023-05-26 10:00:52 Age [y:d:h:m:s]: 01:173:00:01:21
Block: 768426 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385029 RingCT/type: yes/0
Extra: 017a96cda2ca3c51788c70cac4ffc6351bfd0c4441d9064dca81c0cf5d78c4c510021100000001e6d27f9c000000000000000000

1 output(s) for total of 1.745363339000 dcy

stealth address amount amount idx
00: b5cf105875c223bce9016aa0cdbe1eb4cccf33aa1132cc2f2dd8e9dde654e62f 1.745363339000 1217621 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": 768436, "vin": [ { "gen": { "height": 768426 } } ], "vout": [ { "amount": 1745363339, "target": { "key": "b5cf105875c223bce9016aa0cdbe1eb4cccf33aa1132cc2f2dd8e9dde654e62f" } } ], "extra": [ 1, 122, 150, 205, 162, 202, 60, 81, 120, 140, 112, 202, 196, 255, 198, 53, 27, 253, 12, 68, 65, 217, 6, 77, 202, 129, 192, 207, 93, 120, 196, 197, 16, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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