Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1e13afdc2bcb279cc1bb40256181e3da698aab4a20fa49bd7ecf4e6eac8a252

Tx prefix hash: 559659d49e8e9899e810ad62509b21e39bfe31dac9422ae37d4a30eff01cc35b
Tx public key: f7c7c17fcdac3e6a92cfb0b3af2eff99f419c1ed54b775405b3ae26f57cd6ee1
Timestamp: 1695660831 Timestamp [UCT]: 2023-09-25 16:53:51 Age [y:d:h:m:s]: 01:233:11:17:45
Block: 855970 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427942 RingCT/type: yes/0
Extra: 01f7c7c17fcdac3e6a92cfb0b3af2eff99f419c1ed54b775405b3ae26f57cd6ee1021100000001faf35c9c000000000000000000

1 output(s) for total of 0.894985724000 dcy

stealth address amount amount idx
00: 540f9296d1c3d2d3bef670163fcba5f9847b7d4db685b9b916a33ffedc93a51d 0.894985724000 1310022 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": 855980, "vin": [ { "gen": { "height": 855970 } } ], "vout": [ { "amount": 894985724, "target": { "key": "540f9296d1c3d2d3bef670163fcba5f9847b7d4db685b9b916a33ffedc93a51d" } } ], "extra": [ 1, 247, 199, 193, 127, 205, 172, 62, 106, 146, 207, 176, 179, 175, 46, 255, 153, 244, 25, 193, 237, 84, 183, 117, 64, 91, 58, 226, 111, 87, 205, 110, 225, 2, 17, 0, 0, 0, 1, 250, 243, 92, 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