Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b24a99397c0bc43fd005c0d5d647c6c4270dc30e0d53af022eb3f3da4512b46f

Tx prefix hash: 97ad0cc43555d43d47e3f05f07e2c45f283adeb887a646d497023d68a280acfc
Tx public key: 7fa700de59794d0c223a48c7a38b3844deba0048b2bc023d1666efaf75217b9c
Timestamp: 1729084191 Timestamp [UCT]: 2024-10-16 13:09:51 Age [y:d:h:m:s]: 00:099:00:17:54
Block: 1132886 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70710 RingCT/type: yes/0
Extra: 017fa700de59794d0c223a48c7a38b3844deba0048b2bc023d1666efaf75217b9c021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c09adb51e1235fc1025285ed0ff0dee8b25d8f5136f8dbc17df2d5b50b268284 0.600000000000 1615911 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": 1132896, "vin": [ { "gen": { "height": 1132886 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c09adb51e1235fc1025285ed0ff0dee8b25d8f5136f8dbc17df2d5b50b268284" } } ], "extra": [ 1, 127, 167, 0, 222, 89, 121, 77, 12, 34, 58, 72, 199, 163, 139, 56, 68, 222, 186, 0, 72, 178, 188, 2, 61, 22, 102, 239, 175, 117, 33, 123, 156, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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