Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcad5c3c3b047117fdfb5c66118c777596997b3e9989d46497900fb338d529c6

Tx prefix hash: 85d146c1f54702f8dcc25390f4c40103e8a386eeefd752ad57993681291eedd9
Tx public key: 8b9dfa796768f21ac15d6e64b10e2d53de912d437c329bf8f640bc56a6845f6d
Timestamp: 1705795914 Timestamp [UCT]: 2024-01-21 00:11:54 Age [y:d:h:m:s]: 01:150:08:46:08
Block: 939763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368480 RingCT/type: yes/0
Extra: 018b9dfa796768f21ac15d6e64b10e2d53de912d437c329bf8f640bc56a6845f6d021100000003abeff91a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 68580209244add8c444b1e8e7a95e3f59710c8d2c3a127b3da05149ee26da744 0.600000000000 1397893 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": 939773, "vin": [ { "gen": { "height": 939763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "68580209244add8c444b1e8e7a95e3f59710c8d2c3a127b3da05149ee26da744" } } ], "extra": [ 1, 139, 157, 250, 121, 103, 104, 242, 26, 193, 93, 110, 100, 177, 14, 45, 83, 222, 145, 45, 67, 124, 50, 155, 248, 246, 64, 188, 86, 166, 132, 95, 109, 2, 17, 0, 0, 0, 3, 171, 239, 249, 26, 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