Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7e22ad034ed7292daf4626b2833605be1b99895c24da89189959c9d17f1565c6

Tx prefix hash: e80c89854377eecb34de14803969f2155c3aa91d4193a8b4cf574cad59ccf01d
Tx public key: 0b814e5d2e0e731af66389e619ae5f1d82cf14ddbd3ae0e9b51a35e9a11cb1de
Timestamp: 1701676662 Timestamp [UCT]: 2023-12-04 07:57:42 Age [y:d:h:m:s]: 01:151:02:27:52
Block: 905637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369171 RingCT/type: yes/0
Extra: 010b814e5d2e0e731af66389e619ae5f1d82cf14ddbd3ae0e9b51a35e9a11cb1de0211000000014b8f5122000000000000000000

1 output(s) for total of 0.612701081000 dcy

stealth address amount amount idx
00: 705b74bc09b4c619d416ca8ea694e375a2040ba8adc5cc872c37fd9efd6556c0 0.612701081000 1362532 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": 905647, "vin": [ { "gen": { "height": 905637 } } ], "vout": [ { "amount": 612701081, "target": { "key": "705b74bc09b4c619d416ca8ea694e375a2040ba8adc5cc872c37fd9efd6556c0" } } ], "extra": [ 1, 11, 129, 78, 93, 46, 14, 115, 26, 246, 99, 137, 230, 25, 174, 95, 29, 130, 207, 20, 221, 189, 58, 224, 233, 181, 26, 53, 233, 161, 28, 177, 222, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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