Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f46943b8084e12aae585eb81cea0a271ac9a1c1e5666fa9d0710a021be5b8493

Tx prefix hash: ab4c1d10d7cd31b6ed76596494ffef751350e374211d7cb3b6b97df2c8f19a39
Tx public key: fafaa71ae0e2fe574beb91690ba7bd8a0fa4aa69a412c1cb54ac26fbf3d6f6e1
Timestamp: 1720489214 Timestamp [UCT]: 2024-07-09 01:40:14 Age [y:d:h:m:s]: 01:122:12:30:16
Block: 1061626 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 346070 RingCT/type: yes/0
Extra: 01fafaa71ae0e2fe574beb91690ba7bd8a0fa4aa69a412c1cb54ac26fbf3d6f6e102110000000c91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 944ee77bbb82c3c2474f589b17fed4c607370dac0e14aa1ac30f0eebd1be6aa8 0.600000000000 1532119 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": 1061636, "vin": [ { "gen": { "height": 1061626 } } ], "vout": [ { "amount": 600000000, "target": { "key": "944ee77bbb82c3c2474f589b17fed4c607370dac0e14aa1ac30f0eebd1be6aa8" } } ], "extra": [ 1, 250, 250, 167, 26, 224, 226, 254, 87, 75, 235, 145, 105, 11, 167, 189, 138, 15, 164, 170, 105, 164, 18, 193, 203, 84, 172, 38, 251, 243, 214, 246, 225, 2, 17, 0, 0, 0, 12, 145, 225, 60, 4, 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