Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f91827e155ae550df5cab3104ed2a2ff28dbe9d51854ce4dd664885351f68d2b

Tx prefix hash: 1593633492f8842b468832a008abf3dd6494dc8a91d0ed1e77e66b17c77dfb8a
Tx public key: 11003325b1f766cd959177f2dd347d2e4ee221ec1c2bb2fed458aad84684207d
Timestamp: 1695560695 Timestamp [UCT]: 2023-09-24 13:04:55 Age [y:d:h:m:s]: 01:129:01:44:45
Block: 855145 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353276 RingCT/type: yes/0
Extra: 0111003325b1f766cd959177f2dd347d2e4ee221ec1c2bb2fed458aad84684207d021100000002faf35c9c000000000000000000

1 output(s) for total of 0.900636776000 dcy

stealth address amount amount idx
00: 70f732b948e8dd1d99814605e0a6e2bf728c9dcdb24c901e67ae3aa01ce355f4 0.900636776000 1309149 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": 855155, "vin": [ { "gen": { "height": 855145 } } ], "vout": [ { "amount": 900636776, "target": { "key": "70f732b948e8dd1d99814605e0a6e2bf728c9dcdb24c901e67ae3aa01ce355f4" } } ], "extra": [ 1, 17, 0, 51, 37, 177, 247, 102, 205, 149, 145, 119, 242, 221, 52, 125, 46, 78, 226, 33, 236, 28, 43, 178, 254, 212, 88, 170, 216, 70, 132, 32, 125, 2, 17, 0, 0, 0, 2, 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