Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77c88e2abe78c72513e09cfa3edda9f4607b7c623c2781c752609e6526f6e8e0

Tx prefix hash: 326933fabdef06a2384580d812ebe91db651fb62b3ba8a7f940254e3dfc18329
Tx public key: 565a4b6ed26dc2130d97e4f678dbd463aef8bb332189b737b697e921d8b032ec
Timestamp: 1708904950 Timestamp [UCT]: 2024-02-25 23:49:10 Age [y:d:h:m:s]: 01:253:10:21:54
Block: 965577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 439841 RingCT/type: yes/0
Extra: 01565a4b6ed26dc2130d97e4f678dbd463aef8bb332189b737b697e921d8b032ec0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85f2e871ef7291d75c9c0861a129ba8e1c1dc7913dcbb84d9a6c5bde9a3a2aca 0.600000000000 1425330 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": 965587, "vin": [ { "gen": { "height": 965577 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85f2e871ef7291d75c9c0861a129ba8e1c1dc7913dcbb84d9a6c5bde9a3a2aca" } } ], "extra": [ 1, 86, 90, 75, 110, 210, 109, 194, 19, 13, 151, 228, 246, 120, 219, 212, 99, 174, 248, 187, 51, 33, 137, 183, 55, 182, 151, 233, 33, 216, 176, 50, 236, 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