Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01a514f1fadb4ae97cbceb6fded99000cfe81457d18571bc8377152b67ffb0ef

Tx prefix hash: ad04e6fe312fb9ec4cc798f480feb79d51456253e721c5f07dd470e20e9c8bfd
Tx public key: a1746db5262382661c93552df22af85c1db4dc0a9ee648d5aeb61f9c0019bc19
Timestamp: 1738143485 Timestamp [UCT]: 2025-01-29 09:38:05 Age [y:d:h:m:s]: 00:342:20:51:54
Block: 1207561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242870 RingCT/type: yes/0
Extra: 01a1746db5262382661c93552df22af85c1db4dc0a9ee648d5aeb61f9c0019bc190211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d1fb401fbf9f3094dae6f7f8b630c0b806b6b9ffb2baef38c90457fa3106792 0.600000000000 1694286 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": 1207571, "vin": [ { "gen": { "height": 1207561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d1fb401fbf9f3094dae6f7f8b630c0b806b6b9ffb2baef38c90457fa3106792" } } ], "extra": [ 1, 161, 116, 109, 181, 38, 35, 130, 102, 28, 147, 85, 45, 242, 42, 248, 92, 29, 180, 220, 10, 158, 230, 72, 213, 174, 182, 31, 156, 0, 25, 188, 25, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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