Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39f4c5fc9f28b933a0706b438b385ab2c3c4cefa75f86f27d398b94334a65c5c

Tx prefix hash: 46be9d8f44aece7258e58ac06704d8ca3a1599cd1410310cda0b58378b123108
Tx public key: cf9bf75d19ad5e9cb35165be64c41dfdc37f166bc3160f916917bffe0a96d0f9
Timestamp: 1727852369 Timestamp [UCT]: 2024-10-02 06:59:29 Age [y:d:h:m:s]: 00:162:04:17:42
Block: 1122658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115714 RingCT/type: yes/0
Extra: 01cf9bf75d19ad5e9cb35165be64c41dfdc37f166bc3160f916917bffe0a96d0f902110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87dd320ddc8d9d3ebd96bb7865a46bd12682e6555b5b9b96532a4d8b399c4662 0.600000000000 1605143 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": 1122668, "vin": [ { "gen": { "height": 1122658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87dd320ddc8d9d3ebd96bb7865a46bd12682e6555b5b9b96532a4d8b399c4662" } } ], "extra": [ 1, 207, 155, 247, 93, 25, 173, 94, 156, 179, 81, 101, 190, 100, 196, 29, 253, 195, 127, 22, 107, 195, 22, 15, 145, 105, 23, 191, 254, 10, 150, 208, 249, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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